8364107: [lworld] Revise memory limit in compiler/startup/StartupOutput.java #1749
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's do a similar job as in #1509 and see what evolved since JDK-8350209: Preserve adapters in AOT cache landed in Valhalla.
For each tick in the list, I give a range that behaves homogeneously, and compare it to a Mainline and/or Valhalla range of #1509
[4, 24] ~ Mainline [4, 28]
[25, 28] ~ Mainline [29, 32] | Valhalla [29, 32]
fatal error: Initial size of CodeCache is too small[29, 1164] ~ Mainline [33, 1112] | Valhalla [33, 1164]
[1165, 1172] ~ Mainline [1117, 1128] | Valhalla [1165, 1172]
fatal error: Initial size of CodeCache is too small[1173, 1176] ~ Valhalla [1225, 1228] (out of order, weird, uh!)
SIGSEGV in
CodeSection::emit_int8(unsigned char)[1177, 1224] ~ Mainline [1129, 1144] | Valhalla [1173, 1220]
assert(_buffer != nullptr) failed: should be initialized[1225, 1228] ~ Mainline [1145, 1148] | Valhalla [1221, 1224]
assert(_no_arg_handler != nullptr && _obj_arg_handler != nullptr && _int_arg_handler != nullptr && _obj_int_arg_handler != nullptr && _obj_obj_arg_handler != nullptr) failed: Initial adapter handlers must be properly created[1229, ~1250] ~ Mainline [1149, ~1700]
Often works, sometimes
[~1250, 1276]
Mostly works
[1277, 1432]
[1433, 1438] ~ Valhalla [1301, 1308]
[1439, ~1600]
works but
Above 1600, compiler shutdown starts to be rare, but again around 2800k Like it was for Valhalla before above 1994k, and we saw it around 3700k.
It used to be:
Overall, the behavior for small amount of memory is similar as in previous Valhalla and mainline. The behavior for larger amounts got much better, more similar to mainline where it mostly works from 1149k, and up, except in some pathological islands.
So, it looks good to reduce the
2000incompiler/startup/StartupOutput.java(was increased from800). So, I just tried... If locally, I could indeed make it run with quite smaller amount of memory, some more testing shows that1300is a better bound: it crashes significantly starting under1200but seems to pass all tests with1300. That is still an increase from800, but less radical than2000.Thanks,
Marc
Progress
Integration blocker
8364107. Please make sure it exists and is accessible.Issue
8364107.Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/valhalla.git pull/1749/head:pull/1749$ git checkout pull/1749Update a local copy of the PR:
$ git checkout pull/1749$ git pull https://git.openjdk.org/valhalla.git pull/1749/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1749View PR using the GUI difftool:
$ git pr show -t 1749Using diff file
Download this PR as a diff file:
https://git.openjdk.org/valhalla/pull/1749.diff